Announce a finished transcript in the meeting pill - #9
Merged
Conversation
The daemon fired an osascript notification when a recorded session finished transcribing, which lands in Notification Center looking like it came from Script Editor and gives you nowhere to click. Reuse the pill the meeting prompt already draws: same panel, same placement under the menu bar, a Glass chime, and one Open button that reveals transcript.md in Finder. No Dismiss — an announcement has nothing to decline, so it leaves on its own after six seconds. A live prompt is a question and must not be covered by an announcement, so a toast arriving while one is up falls back to the notification; a prompt arriving evicts the toast, since both occupy the same spot. The coordinator learns one injectable handler, mirroring setStatusHandler. One-shot `yap record` sets none and keeps the notification: it has no AppKit run loop, and a failure should persist rather than vanish in six seconds — so the failure branch stays on notifyUser too.
This was referenced Aug 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The daemon fired an osascript
display notificationwhen a recorded session finished transcribing, which lands in Notification Center attributed to Script Editor and gives you nowhere to click.This reuses the pill the meeting prompt already draws — same
PromptPanel, same placement under the menu bar, plus a Glass chime and one Open button that revealstranscript.mdin Finder. No Dismiss: an announcement has nothing to decline, so it leaves on its own after six seconds.No new file, no new class, no new dependency.
PromptPanelgains atoast: Boolthat drops the Dismiss button and swaps the 120 s prompt lifetime for 6 s; the coordinator gains one injectable handler mirroringsetStatusHandler.Collision rules
Both live top-centre, so:
What deliberately did not change
yap recordsets no handler and keeps the notification: it is aParsableCommandwith no AppKit run loop.notifyUser— a failure should persist in Notification Center, not vanish in six seconds.Verification
On an M4, against the resume path (delete
transcript.json/.mdfrom a session, relaunch the daemon, it re-transcribes at startup):[Open], at790,56— confirming the Dismiss button is omitted and the panel sits under the menu bar;document file "transcript.md" of folder "2026.07.31-1216"— the right file in the right session;yap record --out /tmp/…still transcribes and notifies, no pill;NSSound(named: "Glass")?.play()as a temporary was checked rather than assumed: a weak reference to it stays alive withisPlaying == trueafter the only local reference dies, so AppKit retains it for the duration and no stored property is needed.No audio or transcription path touched, so the benchmark table is unaffected.
Full local CI gate green before pushing:
swift test,swift build -c release --arch arm64, the three smoke subcommands, and the embedded__info_plistcheck.